-
-
Notifications
You must be signed in to change notification settings - Fork 3.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Text to model docs #7595
base: dev-2.0
Are you sure you want to change the base?
Text to model docs #7595
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hi @perminder-17 thanks, it looks good, I just added a small comment about notation and a need for a small clarification, let me know your thoughts.
CC: @davepagurek @limzykenneth
* 'vec4 getFinalColor': `(vec4 _c) { | ||
* float x = vPos.x * 0.005; | ||
* float a = floor(fract(x) * numColors); | ||
* float b = a == numColors - 1. ? 0. : a + 1.; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Not sure if this was adressed before, but having the notation -1.
might not be clear for all users, thinking that why not use just -1
or -1.0
I understand that we might need to explicitly cast it like this to indicate its a float to WEBGL but it might I think it would be useful to add a note as to why we choose to notate it like this. A brief comment would be good enough I believe
* | ||
* let prevWords = ''; | ||
* let prevFont = ''; | ||
* let prevExtrude = -1; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
for example, why in the other cases we need an explicit float and not here? It might be confusing for some users.
No description provided.